ProStructures Project Migration
In SS8, ProStructures projects were the mechanism for associating (steel) models with their output, e.g. details and partlists, and supporting data files, e.g. templates and styles. Settings for one project could be changed without impacting other projects or the underlying dataset (localization) and vice versa.
ProStructures projects are not supported in the CONNECT Edition. The functionality is replaced and greatly expanded by the organization-centric configuration setup and the new configuration variables. The recommendation is to migrate an SS8 ProStructures project to the CONNECT Edition as a workset in the ProStructures-extended workspace most like the original SS8 localization.
The following table lists the default folders in an SS8 ProStructures project and where the files should be moved for the CONNECT Edition. Related CONNECT Edition configuration variables are also listed.
| Project Migration | |
|---|---|
| …\WorkSpace\ProStructures\Projects\projectName\ | |
| +
Details\
| |
$(PS_DETAILPATH)
Move contents to workSet\Out\Details\ |
| +
ERP\
| |
$(PS_PPSPATH)
Move contents to workSet\Out\ERP-PPS\ |
| +
Export\
| |
$(PS_EXPORTPATH)
Move contents to workKSet\Out\Export\ |
| + Format\ | If exists, see "Project Data Files" below. |
| +
Model\
| + xxx.dgn |
$(_USTN_WORKSETDGNS)
Move to workSet\Dgn\ |
| +
NC\
| |
$(PS_NCPATH)
Move contents to workSet\Out\NC\ |
| +
Partlist\
| + xxx.mdb | + xxx & xxx\ |
$(PS_PARTLISTDATABASE) for
.mdb files
Move to workSet\Out\Partlist\ If any exist, see "Project Data Files" below. |
| + Styles\ | If exists, see "Project Data Files" below. |
| + Temp\ | |
| + Varia\ | |
Project Data Files
The general instructions for migrating a project data file folder to a workset is to mimic how the source dataset folder was migrated to a workspace:
- Move files (that weren't moved to product\Default\xxx\) to workSet\Standards\ProStructures\xxx\.
- Set matching configuration variables in a workset configuration file.
- Delete any obsolete files.
The following are optional refinements to the general instructions:
- If none of the files related to a configuration variable are, or need to be, different in the workset (from the workspace), the files don't need to be migrated and the configuration variable setting should be left alone.
- If the configuration variable is a directory list type, only the files that are, or could be, different from the workspace need to be migrated. The workset directory should be prepended to the configuration variable in a workset configuration file.